<?xml version="1.0" encoding="UTF-8"?><!-- Copyright 2005 XBRL International. All Rights Reserved. --><?xml-stylesheet type="text/xsl" href="../../testcase.xsl"?><testcase xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xbrldte="http://xbrl.org/2005/xbrldt/errors"  name="107-TestCase-TargetRoleNotResolvedError" description="2.1 to 2.10 - Dimensional relationships except 2.5" outpath="out" owner="ihr@xbrl.org" minimal="true" xsi:schemaLocation="http://xbrl.org/2005/conformance ../../lib/test.xsd">
<!-- Dimensional taxonomy syntax rules pertaining to schemas and linkbases, and not covered by XML Schema and XBRL Validation. -->
        <!-- Note that XBRL validation requires the source and target of a definitionArc to be a concept. -->
        <!-- As of the 2005-10-26 internal working draft. (Herm) -->
        <!-- 2.4 Taxonomy authors are able to partition relationships into distinct base sets using the xlink:role attribute on extended-type link elements. -->
        <variation id="V-01" name="hypercubeDimensionTargetRoleValid">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">The value of the xbrldt:targetRole attribute is valid</description>
                <data>
                        <xsd readMeFirst="true">hypercubeDimensionTargetRoleValid.xsd</xsd>
                        <linkbase readMeFirst="false">hypercubeDimensionTargetRoleValid-definition.xml</linkbase>
                        <linkbase readMeFirst="false">hypercubeDimensionTargetRoleValid-label.xml</linkbase>
                </data> 
                <result />
        </variation>
        <!-- 2.4.3 1. A dimensional processor MUST raise an error [Dim Err, 10] xbrldte:TargetRoleNotResolvedError if the URI content of an xbrldt:targetRole attribute cannot be resolved via a roleRef element (3.5.2.4 [XBRL]) to a roleType element (5.1.3 [XBRL]) -->
        <variation id="V-02" name="hypercubeDimensionTargetRoleNotResolved">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">The value of the xbrldt:targetRole attribute is valid. The test case is invalid because it contains a targetrole attribute whose value is http://www.xbrl.org/dim/conf/role/foobar but there is no a roleRef declaration</description>
                <data>
                        <xsd readMeFirst="true">hypercubeDimensionTargetRoleNotResolved.xsd</xsd>
                        <linkbase readMeFirst="false">hypercubeDimensionTargetRoleNotResolved-definition.xml</linkbase>
                        <linkbase readMeFirst="false">hypercubeDimensionTargetRoleNotResolved-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
        </variation>
        <variation id="V-03" name="hasHypercubeTargetRoleValid">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">An all hypercube has a targetRole attribute to locate the domain - dimension arc network.</description>
                <data>
                        <xsd readMeFirst="true">hasHypercubeTargetRoleValid.xsd</xsd>
                        <linkbase readMeFirst="false">hasHypercubeTargetRoleValid-definition.xml</linkbase>
                        <linkbase readMeFirst="false">hasHypercubeTargetRoleValid-label.xml</linkbase>
                </data>
                <result/>
        </variation>
        <!-- 2.3.4 1.   A dimensional processor MUST raise an error [Dim Err, 10] xbrldte:TargetRoleNotResolvedError if the URI content of an xbrldt:targetRole attribute cannot be resolved via a roleRef element (3.5.2.4 [XBRL]) to a roleType element (5.1.3 [XBRL]) -->
        <variation id="V-04" name="hasHypercubeTargetRoleNotResolved">
                <description reference="XDT-IWD-2005-10-26.doc#2.3.4.1">An all hypercube has a well-formed but bogus targetRole attribute to locate the domain - dimension arc network.</description>
                <data>
                        <xsd readMeFirst="true">hasHypercubeTargetRoleNotResolved.xsd</xsd>
                        <linkbase readMeFirst="false">hasHypercubeTargetRoleNotResolved-definition.xml</linkbase>
                        <linkbase readMeFirst="false">hasHypercubeTargetRoleNotResolved-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
        </variation>
        <!-- 2.4 As declared in their LRR entries, the xbrldt:targetRole attribute MAY appear on definition arcs having the following arc roles: ... -->
        <variation id="V-05" name="dimensionDomainTargetRoleValid">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">A dimension-domain relationship has a targetRole attribute to locate the domain member arc network.</description>
                <data>
                        <xsd readMeFirst="true">dimensionDomainTargetRoleValid.xsd</xsd>
                        <linkbase readMeFirst="false">dimensionDomainTargetRoleValid-definition.xml</linkbase>
                        <linkbase readMeFirst="false">dimensionDomainTargetRoleValid-label.xml</linkbase>
                </data>
                <result/>
        </variation>
        <!-- 2.3.4 1.   A dimensional processor MUST raise an error [Dim Err, 10] xbrldte:TargetRoleNotResolvedError if the URI content of an xbrldt:targetRole attribute cannot be resolved via a roleRef element (3.5.2.4 [XBRL]) to a roleType element (5.1.3 [XBRL]) -->
        <variation id="V-06" name="dimensionDomainTargetRoleNotResolved">
                <description reference="XDT-IWD-2005-10-26.doc#2.3.4.1">A dimension-domain relationship has a well-formed but bogus targetRole attribute to locate the domain - member arc network.</description>
                <data>
                        <xsd readMeFirst="true">dimensionDomainTargetRoleNotResolved.xsd</xsd>
                        <linkbase readMeFirst="false">dimensionDomainTargetRoleNotResolved-definition.xml</linkbase>
                        <linkbase readMeFirst="false">dimensionDomainTargetRoleNotResolved-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
        </variation>
        <!-- 2.4 As declared in their LRR entries, the xbrldt:targetRole attribute MAY appear on definition arcs having the following arc roles: ... -->
        <variation id="V-07" name="domainMemberTargetRoleValid">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">A domain-member relationship has a targetRole attribute to locate the domain member arc network.</description>
                <data>
                        <xsd readMeFirst="true">domainMemberTargetRoleValid.xsd</xsd>
                        <linkbase readMeFirst="false">domainMemberTargetRoleValid-definition.xml</linkbase>
                        <linkbase readMeFirst="false">domainMemberTargetRoleValid-label.xml</linkbase>
                </data>
                <result/>
        </variation>
        <!-- 2.3.4 1.   A dimensional processor MUST raise an error [Dim Err, 10] xbrldte:TargetRoleNotResolvedError if the URI content of an xbrldt:targetRole attribute cannot be resolved via a roleRef element (3.5.2.4 [XBRL]) to a roleType element (5.1.3 [XBRL]) -->
        <variation id="V-08" name="domainMemberTargetRoleNotResolved">
                <description reference="XDT-IWD-2005-10-26.doc#2.3.4.1">A domain-member relationship has a well-formed but bogus targetRole attribute to locate the domain - member arc network.</description>
                <data>
                        <xsd readMeFirst="true">domainMemberTargetRoleNotResolved.xsd</xsd>
                        <linkbase readMeFirst="false">domainMemberTargetRoleNotResolved-definition.xml</linkbase>
                        <linkbase readMeFirst="false">domainMemberTargetRoleNotResolved-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
        </variation>
        <variation id="V-09" name="notAllHasHypercubeTargetRoleValid">
                <description reference="XDT-IWD-2005-10-26.doc#2.4">A notAll hypercube has a targetRole attribute to locate the domain - dimension arc network.</description>
                <data>
                        <xsd readMeFirst="true">notAllHasHypercubeTargetRoleValid.xsd</xsd>
                        <linkbase readMeFirst="false">notAllHasHypercubeTargetRoleValid-definition.xml</linkbase>
                        <linkbase readMeFirst="false">notAllHasHypercubeTargetRoleValid-label.xml</linkbase>
                </data>
                <result/>
        </variation>
        <!-- 2.3.4 1.   A dimensional processor MUST raise an error [Dim Err, 10] xbrldte:TargetRoleNotResolvedError if the URI content of an xbrldt:targetRole attribute cannot be resolved via a roleRef element (3.5.2.4 [XBRL]) to a roleType element (5.1.3 [XBRL]) -->
        <variation id="V-10" name="notAllHasHypercubeTargetRoleNotResolved">
                <description reference="XDT-IWD-2005-10-26.doc#2.3.4.1">A notAll hypercube has a well-formed but bogus targetRole attribute to locate the domain - dimension arc network.</description>
                <data>
                        <xsd readMeFirst="true">notAllHasHypercubeTargetRoleNotResolved.xsd</xsd>
                        <linkbase readMeFirst="false">notAllHasHypercubeTargetRoleNotResolved-definition.xml</linkbase>
                        <linkbase readMeFirst="false">notAllHasHypercubeTargetRoleNotResolved-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
        </variation>
        <variation id="V-11" name="domainMemberTargetRoleMissingRoleRef">
                <description reference="XDT-CR4-2006-07-20.doc#2.4.3">A domain-member has a targetRole attribute to locate the domain - member arc network, but the roleRef for the targetRole is commented out in the linkbase containing the targetRole, to force the error message.</description>
                <data>
                        <xsd readMeFirst="true">domainMemberTargetRoleMissingRoleRef.xsd</xsd>
                        <linkbase readMeFirst="false">domainMemberTargetRoleMissingRoleRef-definition.xml</linkbase>
                        <linkbase readMeFirst="false">domainMemberTargetRoleMissingRoleRef-definition2.xml</linkbase>
                        <linkbase readMeFirst="false">domainMemberTargetRoleMissingRoleRef-label.xml</linkbase>
                </data>
                <result >
                        <error>xbrldte:TargetRoleNotResolvedError</error>
                </result>
       </variation>
        <variation id="V-12" name="unconnectedDRS">
                <description reference="XDT-REC-2006-09-18+Corrected-Errata-2007-03-29.doc#2.4">Two arcs that represent a consecutive relationship [Def, 2] that exist in different extended-type link elements MUST be connected together using the xbrldt:targetRole attribute. Not doing so causes the construction to be unconnected and results in, for example, empty hypercubes, dimensions and domains. Some tools may raise a warning.</description>
                <data>
                        <xsd readMeFirst="true">unconnectedDRS.xsd</xsd>
                        <linkbase readMeFirst="false">unconnectedDRS-definition.xml</linkbase>
                </data>
                <result/>
       </variation>
</testcase>

